v0.11.0

Compare Source

What's Changed

🔬 Improvements

• Fix non pr comments by @​formaceft-93 in #​106

⬆️ Dependency Updates

• Bump oxfmt from 0.62.0 to 0.68.0 by @​dependabot[bot] in #​102
• Bump tsdown from 0.22.3 to 0.23.0 by @​dependabot[bot] in #​105
• Bump @​types/node from 26.6.1 to 26.6.3 by @​dependabot[bot] in #​104
• Bump vitest from 4.1.11 to 5.0.2 by @​dependabot[bot] in #​103

👻 Internal changes

• fix: declare vite dev dependency by @​formaceft-93 in #​107

Full Changelog: allure-framework/allure-action@v0.10.3...v0.11.0

v0.10.3

Compare Source

What's Changed

👻 Internal changes

• fix: tolerate incomplete report summaries by @​formaceft-93 in #​100

Full Changelog: allure-framework/allure-action@v0.10.2...v0.10.3

v0.10.2

Compare Source

What's Changed

👻 Internal changes

• fix: handle omitted report summary names by @​formaceft-93 in #​99

Full Changelog: allure-framework/allure-action@v0.10.1...v0.10.2

v0.10.1

Compare Source

What's Changed

🔬 Improvements

• use Allure 3.18 shared report summary renderer by @​formaceft-93 in #​98

⬆️ Dependency Updates

• Bump lefthook from 2.1.9 to 2.1.12 by @​dependabot[bot] in #​97
• Bump oxlint from 1.77.0 to 1.82.0 by @​dependabot[bot] in #​95
• Bump @​types/node from 26.0.0 to 26.6.1 by @​dependabot[bot] in #​94
• Bump @​vitest/snapshot from 4.1.11 to 5.0.1 by @​dependabot[bot] in #​96
• Bump npm-run-all2 from 9.0.2 to 9.0.3 by @​dependabot[bot] in #​87

👻 Internal changes

• use allure-ci app token by @​formaceft-93 in #​93

Full Changelog: allure-framework/allure-action@v0.10.0...v0.10.1

v0.10.0

Compare Source

What's Changed

🔬 Improvements

• widgets GH PR preview by @​formaceft-93 in #​91

⬆️ Dependency Updates

• Bump @​allurereport/plugin-testops from 3.13.2 to 3.14.3 by @​dependabot[bot] in #​79
• Bump oxfmt from 0.56.0 to 0.62.0 by @​dependabot[bot] in #​80

👻 Internal changes

• Improve Allure report notifications by @​formaceft-93 in #​92

Full Changelog: allure-framework/allure-action@v0.9.0...v0.10.0

v2.16.2

Compare Source

🐞 Bug Fixes

• fix(pytest-bdd): do not reuse uuid across test runs (via #​926) - @​delatrie

👀 Links

Commits since 2.16.1

v2.16.1

Compare Source

• Write Allure result files atomically (via #​924) - @​delatrie
• Fix fixture tests for allure_pytest failing against pytest 9.1 (via #​916) - @​delatrie

👀 Links

Commits since 2.16.0

v0.17.0

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.17.0

v0.16.10

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.10

v0.16.9

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.9

v0.16.8

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.8

v0.16.7

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.7

v0.16.6

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.6

v0.16.5

Compare Source

See: https://github.com/astral-sh/ruff/releases/tag/0.16.5

v10.3.0: 🌈 Add Python architecture selection

Compare Source

Changes

This release adds the python-arch input to select a Python architecture independently of the Python version. With uv 0.13.0 or later, set python-arch: x86_64 to use x64 Python on Windows ARM64 runners.

It also includes embedded checksums for uv releases through 0.13.0.

• Use macOS 15 runners for tests @​charliermarsh (#​1081)

🚀 Enhancements

• Add python-arch support @​zanieb (#​1079)

🧰 Maintenance

• chore: update known checksums for 0.13.0 @​github-actions[bot] (#​1089)
• chore: update known checksums for 0.12.24 @​github-actions[bot] (#​1084)
• chore: update known checksums for 0.12.23 @​github-actions[bot] (#​1082)
• chore: update known checksums for 0.12.22 @​github-actions[bot] (#​1080)
• chore: update known checksums for 0.12.21 @​github-actions[bot] (#​1078)
• chore: update known checksums for 0.12.20 @​github-actions[bot] (#​1076)
• chore: update known checksums for 0.12.19 @​github-actions[bot] (#​1068)
• chore: update known checksums for 0.12.18 @​github-actions[bot] (#​1065)

⬆️ Dependency updates

• chore(deps): bump zizmorcore/zizmor-action from 0.6.2 to 0.6.3 @​dependabot[bot] (#​1077)

v10.2.0: 🌈 Disable automatic cache saves for merge queues

Compare Source

Changes

This release contains the known-checksum of the most recent uv releases and also disabled the uploading(saving) of the cache when in a merge queue since theses caches would almost never be used.

🚀 Enhancements

• Disable automatic cache saves for merge queues @​eifinger (#​1056)

🧰 Maintenance

• chore: update known checksums for 0.12.17 @​github-actions[bot] (#​1058)
• chore: update known checksums for 0.12.16 @​github-actions[bot] (#​1057)
• chore: update known checksums for 0.12.15 @​github-actions[bot] (#​1054)
• chore: update known checksums for 0.12.14 @​github-actions[bot] (#​1053)
• chore: update known checksums for 0.12.13 @​github-actions[bot] (#​1045)

📚 Documentation

• docs: update version references to v10.1.0 @​github-actions[bot] (#​1044)

⬆️ Dependency updates

• chore(deps): roll up Dependabot updates @​eifinger (#​1059)

v10.1.0: 🌈 New output python-runtime-idand respect NO_PROXY

Compare Source

Changes

This release adds more bheind the scene security improvements and also 2 small improvements.

NO_PROXY

This action now respects no_proxy/NO_PROXY environment variables which were previously ignored.

New output python-runtime-id

The new output python-runtime-id can be used to know which python version exactly was installed if you use activate-environment. See pyca/cryptography#15572 (comment) for details on why this can be useful.

🐛 Bug fixes

• fix: respect no proxy directive @​mj0nez (#​1037)
• Use JSON + a typed wrapper instead of TS codegen @​woodruffw (#​1025)

🚀 Enhancements

• Expose a Python "identity" output @​woodruffw (#​1036)
• Verify downloads with astral-sh/versions checksums @​zaniebot (#​1033)

🧰 Maintenance

• chore: update known checksums for 0.12.12 @​github-actions[bot] (#​1041)
• chore: update known checksums for 0.12.10/0.12.11 @​github-actions[bot] (#​1038)
• chore: update known checksums for 0.12.9 @​github-actions[bot] (#​1035)
• chore: update known checksums for 0.12.7/0.12.8 @​github-actions[bot] (#​1031)
• chore: update known checksums for 0.12.6 @​github-actions[bot] (#​1030)
• chore: update known checksums for 0.12.5 @​github-actions[bot] (#​1020)
• Use self-repo syntax for all in-repo actions/reusable workflows @​woodruffw (#​1024)
• Pin one-shot tools @​woodruffw (#​1022)
• ci: remove obsolete direct push attempts @​eifinger (#​1019)

📚 Documentation

• docs: update version references to v10.0.1 @​github-actions[bot] (#​1018)

⬆️ Dependency updates

• chore(deps-dev): roll up Dependabot updates @​eifinger (#​1043)
• Harden npm install defaults @​zaniebot (#​1026)
• Add dependency cooldowns @​woodruffw (#​1021)

v1.63.0

Compare Source

🪟 Locate across frames

page.frame_locator() and frame.frame_locator() called without a selector search in any frame of the
subtree, so you no longer need to locate the iframe first:

# Finds the button in any frame on the page.
page.frame_locator().get_by_role("button").click()

The rest of the locator resolves inside a single frame, just like a regular locator, and an error is thrown when it
matches elements in several frames.

👁️ Visible-only locators

New locator.visible returns a locator that matches only visible elements. It is the recommended
replacement for the :visible CSS pseudo-class:

page.locator("button").visible.click()

🖼️ Aria and screen snapshots in traces

New aria_snapshots and screen_snapshots options of
tracing.start() capture an aria snapshot and a screenshot of the page on every action:

context.tracing.start(snapshots=True, aria_snapshots=True, screen_snapshots=True)

With aria and screen snapshots recorded, the new Display Aria mode in the trace viewer shows the action screenshot
side by side with the aria snapshot, and hovering an aria node highlights it on the screenshot.

New APIs

Browser and Context

• http_credentials now also accepts an array of credentials. The first entry matching the request origin is used, and entries without an origin match any request.
• New option opfs includes the origin private file system in the storage state, so it can be persisted and restored into later contexts.
• New events page.on('dialogclosed') and browserContext.on('dialogclosed') are emitted when a JavaScript dialog is accepted, dismissed or closed by the user.

Command line

• playwright install --no-remove keeps the browsers of other Playwright installations instead of removing them.
• playwright codegen --http-credentials records against pages behind HTTP authentication.

Announcements

• ⚠️ Ubuntu 20.04 is not supported anymore.
• 🐧 On Linux arm64, Playwright now downloads the Chrome for Testing build of Chromium, the same build used on all other platforms.

Browser Versions

• Chromium 153.0.8010.12
• Mozilla Firefox 155.0
• WebKit 26.6

This version was also tested against the following stable channels:

• Google Chrome 153
• Microsoft Edge 153

v0.10.0

Compare Source

Highlights

Traces for playwright.request API contexts (#​333). --tracing now also records contexts created with playwright.request.new_context(), one chunk per test, so a session-scoped API context yields a trace per test. The traces follow the same retain-on-failure handling, trace-N.zip naming and report attachments as browser traces. Requires Playwright 1.60 or newer.

Artifacts in test reports (#​332). Kept screenshots, videos and traces are added to the teardown report as playwright_screenshot, playwright_video and playwright_trace user properties, so --junitxml writes them as <property> elements and pytest_runtest_logreport hooks and reporters can pick them up. With pytest-html >= 4 they are linked from the report, and embedded with --self-contained-html.

Reruns keep their own artifacts (#​331). With pytest-rerunfailures, every attempt now writes to its own folder, test-results/<test>-retry1/ and so on, like Playwright Test. Attempts no longer overwrite each other.

Artifacts survive fixture failures in teardown (#​330). --tracing retain-on-failure, --video retain-on-failure and --screenshot only-on-failure now keep artifacts when a fixture fails during teardown. A test skipped from a fixture no longer counts as failed.

Per-test browser launch options (#​329):

@pytest.mark.parametrize(
    "browser_type_launch_args",
    [{"args": ["--lang=de-DE"]}],
    indirect=True,
)
def test_german(page):
    ...

Each distinct value launches its own browser; command line options such as --headed and --slowmo still apply.

Multi-browser parametrization fixes. Overriding the page fixture no longer drops --browser parametrization on older pytest versions (#​314). browser_name is now parametrized indirectly, so tests keep their original order within a browser (#​284).

VS Code debugger (#​328). The browser is launched headed under the debugger only when a display is available. On Linux without DISPLAY or WAYLAND_DISPLAY set, it stays headless unless --headed is passed.

Breaking changes

• pytest-base-url is now an optional dependency (#​334). The plugin provides --base-url, the base_url ini option, the PYTEST_BASE_URL environment variable and the base_url fixture on its own. --verify-base-url needs the extra:

  pip install pytest-playwright[base-url]

• Minimum pytest version is 7.0 for pytest-playwright and 8.2 for pytest-playwright-asyncio (#​333).

• python-slugify 9.x is now supported (#​324).

Full Changelog: microsoft/playwright-pytest@v0.9.0...v0.10.0

v0.38.2

Compare Source

• Update the version of click declared as a dependency

v0.38.1

Compare Source

• Update vendored schemas: bitbucket-pipelines, buildkite, changie, circle-ci,
  compose-spec, dependabot, github-actions, github-workflows, gitlab-ci, mergify,
  renovate, taskfile, travis, woodpecker-ci (2026-09-20)
• check-jsonschema now has a logo. Thanks to
  Mylah Birdie <https://www.instagram.com/mylahbirdie>__!

v0.17.0

Compare Source

Released on 2026-10-09.

The executables in our macOS and Windows release archives and ruff wheels are now code-signed.
macOS executables are signed with an Apple Developer ID certificate and notarized by Apple. Windows
executables have timestamped Authenticode signatures from Azure Artifact Signing. This enables
verification of the release publisher and binary integrity, supports publisher-based allowlisting,
and should reduce security warnings and antivirus false positives.

Breaking changes

• Update the default and latest Python versions for 3.15 (#​28792)

  Ruff now defaults to Python 3.11 instead of 3.10 when no Python version is configured through
  target-version or
  requires-python. When
  checking for syntax errors without a configured Python version, Ruff now defaults to Python 3.15
  instead of 3.14.

• Update the default rule set (#​28786)

  Several of the flake8-datetimez rules
  (DTZ001,
  DTZ005,
  DTZ006,
  DTZ007,
  DTZ011,
  DTZ012, and
  DTZ901) are no longer enabled by default,
  while undefined-local-with-nested-import-star-usage
  (F406), which corresponds to a syntax error, is now enabled by default.

• Update Rust crate quick-junit to 0.8.0 (#​27295)

  JUnit output now uses a skipped attribute instead of disabled on <testsuite> elements and
  includes a skipped attribute on the root <testsuites> element.

• [flake8-import-conventions] Add datetime as dt as a conventional alias (ICN001) (#​28790)

• Support Unicode dummy variable names (#​28722)

  The default lint.dummy-variable-rgx
  now recognizes underscore-prefixed Unicode names, such as _次, as dummy variables.

• Update to Unicode 17 (#​21229, #​28784)

  Ruff now uses Unicode 17 data for identifier normalization and named character escapes ("\N{...}").

• Always show unsafe and display-only fixes in the CLI (#​27810)

  The default full output format now shows unsafe fixes and suggestions requiring manual review,
  regardless of the unsafe-fixes setting.
  Actually applying unsafe fixes still requires explicit opt-in.

• Remove the Python dependency from conda-forge builds (conda-forge/ruff-feedstock#361)

  The conda-forge build no longer depends on Python, now supports linux-riscv64, win-arm64, and
  linux-ppc64le platforms, and now includes shell completions. However, no longer depending on
  Python means that python -m ruff and import ruff will no longer work. Use ruff directly from
  PATH instead. PyPI installations and those from the standalone installer are unaffected.

• Remove support for ruff-lsp (#​28750)

  Support for ruff-lsp, the legacy Python language server deprecated in Ruff
  v0.9.5, has been removed. The Ruff VS Code
  extension now always uses the native language server; ruff.nativeServer is deprecated and
  ignored. See the migration guide.

Stabilization

The following rules have been stabilized and are no longer in preview:

• lazy-import-mismatch (TID254)
• lazy-import-immediately-resolved
  (TID255)
• os-path-commonprefix (RUF071)

The following behaviors have been stabilized:

• The formatter, unsorted-imports (I001),
  line-too-long (E501), and
  doc-line-too-long (W505) now
  consistently ignore trailing pragma comments when computing line length. This resolved several
  bugs involving interactions between these rules
  (#​27313) but may also cause existing imports to be
  reformatted and was thus classified as a breaking change.

Preview features

• [flake8-bugbear] Report the method name and a more precise range (B005) (#​27050)
• [refurb] Mark fix unsafe and move to suspicious (FURB152) (#​28405)
• [ruff] Allow docstrings in strict mode (RUF067) (#​28679)

Bug fixes

• [flake8-builtins] Expand checks in class scopes (A001) (#​29076)
• [flake8-self] Allow private access on object.__new__(cls) instances (SLF001) (#​29001)
• [flake8-tidy-imports] Skip lazy-import-mismatch in stubs (TID254) (#​29095)
• [flake8-type-checking] Add the notion of runtime-ambiguous references (#​26508)
• [flake8-type-checking] Never flag annotations in function scopes (#​29183)
• [pyflakes] Mark the fix as unsafe when it creates a docstring (F541) (#​28258)
• [pylint] Preserve trailing comments in useless-return fix (PLR1711) (#​29180)
• [ruff] Avoid false positive when pytest.raises is used in a with statement (RUF061) (#​28186)

Rule changes

• [pyupgrade] Suggest typing.TypeForm on Python 3.15 (UP035) (#​29084)

Contributors

• @​DeviousCardi
• @​hugehoo
• @​nekomario28
• @​Daverball
• @​Viicos
• @​DebadityaHait
• @​saberoueslati
• @​baltasarblanco
• @​yxshee
• @​lognd
• @​dor-sr

v0.16.10

Compare Source

Release Notes

Released on 2026-10-01.

Preview features

• Add a migration guide for categories (#​28087)
• [pyupgrade] Add rule for context manager iterator annotations (UP052) (#​29000)

Performance

• Reduce memory used by diagnostics (#​28951)

Server

• Avoid running uv format in untrusted workspaces (#​28873)

Documentation

• Fix links to moved changelog sections and renamed mdtests (#​28941)
• Add Python 3.15 as a supported version (#​28907)
• Add ty as a type checker example (#​28906)

Other changes

• Update Rust toolchain to 1.99 and MSRV to 1.97 (#​29047)

Contributors

• @​ntBre
• @​spaceone
• @​HardMax71
• @​charliermarsh

Install ruff 0.16.10

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.16.10/ruff-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/ruff/releases/download/0.16.10/ruff-installer.ps1 | iex"

Download ruff 0.16.10

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo astral-sh/ruff

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifact> --bundle <file-path of downloaded attestation>

v0.16.9

Compare Source

Release Notes

Released on 2026-09-24.

Preview features

• [ruff] Avoid false positives for overloaded division (RUF069) (#​28309)

Bug fixes

• [flake8-bugbear] Avoid false positives for calls with keyword arguments (B009, B010, B043) (#​28776)
• [flake8-tidy-imports] Allow lazy imports to be used in deferred annotations (TID255) (#​28767)

Rule changes

• Update LibCST-based fixes for Python 3.15 (#​28616)
• [flake8-pyi] Mention stubs in the diagnostic message (PYI002) (#​28542)

Documentation

• Fix horizontal overflow on the rules documentation page (#​28699)
• Update rules table with category information (#​28651)
• [flake8-annotations] Clarify that ANN401 checks return types in addition to arguments (#​28334)
• [flake8-bugbear] Document type-checker interaction (B010) (#​28509)
• [flake8-comprehensions] Document map/generator exception behavior (C417) (#​27794)
• [ruff] Mention related isort settings (RUF022) (#​28719)

Contributors

• @​qinpei-dev
• @​sanjayrohith
• @​ntBre
• @​webdevsamran
• @​zaniebot
• @​ewdurbin
• @​MichaReiser
• @​spaceone
• @​IbrahimKhan12
• @​devtechedge
• @​GruffElixir

Install ruff 0.16.9

Install prebuilt binaries via shell script

curl --proto '=https' --tlsv1.2 -LsSf https://releases.astral.sh/github/ruff/releases/download/0.16.9/ruff-installer.sh | sh

Install prebuilt binaries via powershell script

powershell -ExecutionPolicy Bypass -c "irm https://releases.astral.sh/github/ruff/releases/download/0.16.9/ruff-installer.ps1 | iex"

Download ruff 0.16.9

Verifying GitHub Artifact Attestations

The artifacts in this release have attestations generated with GitHub Artifact Attestations. These can be verified by using the GitHub CLI:

gh attestation verify <file-path of downloaded artifact> --repo astral-sh/ruff

You can also download the attestation from GitHub and verify against that directly:

gh attestation verify <file-path of downloaded artifa

> ❗ **Important**
> 
> ✂ PR body was truncated to here.